Magnum One

home *** CD-ROM | disk | FTP | other *** search

/ Magnum One / Magnum One (Mid-American Digital) (Disc Manufacturing).iso / d19 / smlnet1f.arc / SMLNET.DOC < prev next >

Wrap

Text File | 1989-06-19 | 29.7 KB | 669 lines

Documentation for SMLNET.EXE version 1.F A Netmail/Echomail DoorProgram [06/15/89] This program was created to allow Remote callers (and Sysops) to add, download, edit, read, and search thru Messages quickly. Remote Callers can: Add Public/Private Messages Search thru all messages based on criteria categories Check for New Mail in All Conferences Download all Unread Mail Sysops can: File Attach, File Request, CrashMail messages to any Zone Import Textfiles to the message editor Copy and Delete any message in any conference The program reads the Standard Fido/Opus format (*.Msg) files, and can handle upto 119 conferences with 9999 messages in each conference. It is primarily created to work as RBBS-PC door, but can operate with any BBS system that can create Rod Bowman's Standard Interface Format (RBBS-PC's Dorinfo?.Def), or PCBoard's PCBOARD.SYS file (version 12 and 14). This program somewhat evolved from Bob Wescotts/Rod Bowmans NetDoor program. I thank them for their help, support and understanding for the creation of 'SmlNet'. A Big Thank-you to Mike Davis (8:930/1) who was bold enough to run this program on his 2node bulletin board since Smlnet's earliest beginnings. And for his (many) suggestions and comments (bug finds) during Smlnet's development. He has also written some excellant Docs on how to setup and operate a Net/Echomail System using BinkleyTerm, RBBS-PC, Confmail, OMMM, RBBSPack, SmlNet, Parselst and a few other handy programs. And also to the many others that offered suggestions. Most of them I have been able to implement, but there are some that weren't currently feasible or possible. Quick Start: - UnPack the SmlNet Stuff into its own subdirectory A sample NET.BAT to call Smlnet.exe from Rbbs would be: CD\RBBS\NET COPY \RBBS\DORINFO?.DEF SMLNET %1 CD\RBBS - Using a good Text editor modify SMLNET.CNF to meet your setup. The example CNF file should display very well what you will need to change and what the correct format is. In this CNF file, you will instruct Smlnet the location of 'everything'. Other config/related files are: Smlnet.Adv Smlnet.Zon Smlnet.Nam Smlnet.1st Smlnet.Off Smlnet.Dsz Smlnet.Fos Smlnet.Des - Copy the Smlindex.Exe and Smlmport.Exe files to the mail subdirectory or make them accessible by the Dos's PATH command. Smlindex.Exe will be run after the day's RENUM event. Smlmport.Exe will be run right be the REPLYLNK operation when new mail in imported. - Modify your Binkley.Bat (or frontend mailer batch files...) so that after its does major work or operation such as RENUMbering the Echos, that it will execute the program called SMLINDEX.EXE from the Smlnet subdirectory. such as: Conf3 Renum -S -D 21 F:\mail\DFW_NET -R F:\mail\DFW_NET Conf3 Renum -S -D 21 F:\mail\smlware -R F:\mail\smlware ... SMLINDEX D:\PATH\SMLNET.CNF <- this is what I needed to add Goto Start ... (continue on) (ei. Return to Binkley, ...) where D:\PATH\SMLNET.CNF is the Drive and Path and filename of the smlnet.CNF file. It will read this file to find the list of conferences that it will create smlindex.dat file for. When setup, you should see about 5 time increase in speed when doing the Join/... operations. - run Smlindex.Exe file using the same parameters as above to verify that it is working/setup correctly. - Optional setup of Smlmport.exe file Smlmport.exe is created to update the smlindex.dat files when new mail is received. It is to placed after Confmail (or similar mail tosser) has finished importing new mail. If mail is imported, Confmail creates a Confmail.Out file which contains the list of conferences that has new mail. Smlmport.exe will then read this file to determine which conferences to scan update. a portion of my binkley.bat reads: CONFMAIL Import Areas.bbs -M -F Confmail.out -A Pkxarc If ErrorLevel 2 Goto Severe1 If ErrorLevel 1 Goto Do_Maint Goto End_Import :Do_Maint F: cd \mail SMLMPORT F:\RBBS\NET\SMLNET.CNF CONFMAIL.OUT <<<---- added REPLYLNK -F CONFMAIL.OUT ... where F:\BBS\NET\SMLNET.CNF location of the SMLNET.CNF file where CONFMAIL.OUT name of the conferences to update - To check setup, run SML-CHK, and look at its output files. - To run Smlnet locally, type SMLNET LOCAL - If you find bugs, please let me know. - Have more Fun - ESC key will return you back to the Main Menu from about everywhere - When you get a chance or need to, please read the remainder of these Docs [[[ Limited License ]]] This software is copyrighted but a limited license is granted and you are free to use and share it under the following conditions: 1. SMLNET is not distributed in modified form 2. No fee or other consideration is charged for this program itself 3. Reference to the copyright and author is retained. / 4. IF YOU HAVE NOT YET REGISTERED THEN : ------------------------------ | If your Callers Like this program, OR | If you want updates sent to you, OR | If you need support or answers to problems | then please send $20 to | Darwin Collins | c/o Silicon City RBBS | PO BOX 532293 | Grand Praire, TX | 75053-2293 | | With a donation of at least this amount: | One Year Subscription to: | You will be sent a Registered version and have access to updates | Program support | Automatic Registration to ALL my other DoorGames and Software | Personal Modifications will be done (if possible) | Access to Silicon City RBBS (214)641-2537 [8:930/5] | Since March,89, you can call (214)790-0754 [8:930/20] | (but it is subject to change...) | | If you send a total of $30, then I will send you via Mail all | updates(about every 2 months) for this program and others, | for one year. | | | Bugs and other not-favorables in the program: | If you are registered($30), then you will receive the official | updates. But, I will not send an official update out, whenever | a bug is found.(I will try to keep to 1,2, or 3 month schedule.) | | When a bug is found, and fixed. I will upload the ARCed file to | Silicon City, so that you can download it, if you wish to keep up | with the latest sub-versions. | | The is a Echomail conference called SMLWARE, that also will | try to support this program and others from me. | \------------------------------------------------------------------------- [[[ Warranty ]]] SMLNET is provided "AS IS" without warranty of any kind, either expressed or implied, including, but not limited to the implied warranties of merchantability and fitness for any purpose. The entire risk as to the quality and performance of this program is with the user and should the program prove defective, the user and not the author will assume all responsibility with correcting all information. The author does not warrant that this program will function in the desired mode or will meet any users requirements or that the operation of the program will be error free. But, You are certainly entitled to complain about Bugs you find in this program and Paid Users SHOULD have a BugFree program. This program is written in MicroSoft QuickBasic vr. 2.01, with the DTR patch. This program does not need BRUN20.EXE. The program was optimized for Size and DOES monitor the Carrier. If You Can Not use this Program, (ie. Don't Like it or don't run Doors ) then please make it available for others to Download. Thank You [ My Documentation is not very clearly written, but if you grind ] [ your way thru the program you may find it very very useful. ] SmlNet ( Small NetMail/EchoMail Reader ) comprises of the following files: Files used: SMLNET.EXE Main Program SML-CHK.EXE Check the integrity of the Smlnet.CNF file SMLINDEX.EXE Create a Smlindex.Dat (Index) file for each Echo in each Echo subdirectory SMLMPORT.EXE Update the Smlindex.Dat files if needed SMLNET.DOC (Text) Documentation File SMLNET.TXT (Text) Doc File displayed to Remote Caller SMLNE?.LOG (Text) Log File displaying usage of this program SMLNET.DAT (Binary Data File) contains Message Pointers for all active users. (editible) SMLNET.CNF (Text) CONFIGURATION FILE! (editible) SMLNET.1ST (Text) This file is displayed when program is first entered. (editible) SMLNET.ADV (Text) Configuration file for advertisement file (editible) SMLNET.DES (Text) Description file of available echos (editible) SMLNET.DSZ (Text) Configuration file for DSZ setup (editible) SMLNET.FOS (Text) Configuration file for Fossil setup (editible) SMLNET.NAM (Text) Configuration file for Net/Node/Sysop Name list for Netmail search (editible) SMLNET.OFF (Text) Configuration file for setting Time Range that program should not be used (editible) SMLNET.ZON (Text) Configuration file for MultiZone setup Smlnet.Exe will eat up approximately 250K of your Memory. [[[ Setup of the SmlNet.Cnf File ]]] The Smlnet.Cnf contains everything Smlnet.EXE needs to know about your Net/EchoMail configuration. The sample SmlNet.Cnf should be a very good example of the way that you would like to setup yours. (So hence, just change the necessary fields to match your system setup...) Information you will be inserting into this file is: - Sysop Name Your Name in First LastName format. This is name is only utilized for Local Mode. - Origin line to use for your Netmail conference - Net Number - Node Number - Location of NODELIST.DAT NODELIST.* is used for verifying Net/Node numbers when a message is entered in the NetMail conference. Smlnet uses Version 6 of NODELIST.NDX and NODELIST.DAT file. These files are standard for systems running with Binkley. (With Zones 1,2,3 and 8 included: Nodelist.Ndx was about 23K, Nodelist.Dat was 747K in size.) - Location of the Binkley Outbound Area Subdirectory to use for place .CLO, .HLO, .REQ, & .MO# files. -if NONE, it will only set the flags in the Netmail area, but will not create the the Crash/Freq Packets itself. - Name of Extract file The filename of the Extract file that is used by the remote callers when they X'tract messages into the downloadable file. Highly Recommended to keep to 'ECHOMAIL.TXT'. Drive:\Path is not allowed in option. - Security Access (Minimum for Sysop Access) Any remote caller entering this program with an user security access level equal or greater to the above number is treated as a Sysop. Sysop access includes: Viewing everyone's mail (public and private). Able to Kill any message in the Netmail conference. Manually Delete Users from the Smlnet.dat file. Access for File Attach,Request,CrashMail Importing Files into the message editor - Minimum Security level to 'Enter' or 'Reply' a message If the remote caller is below the specified level then he can read but not write any messages. - Number of months before an inactive caller will be deleted About once a day or so, the program will check for any users that haven't been on for X number of months, and will delete them. Smlchk.exe is used to do the user deletion date check. - Name of Packing Program Name of Squash program (ARC,PKZIP,PKPAK) that you want to use for Squashing Crash, File_Attach, and File_Request messages that you create in the Netmail conference. Type NONE if you don't want to 'squish' the message into a .MO?, and want it to remain a .PKT to be sent out. Valid options are ARC, LHARC, PKPAK, PKZIP, and NONE The program uses Zmodem(DSZ.COM) by Chuck Forsberg for transfering the Squashed Extract file over the Modem lines. So, DSZ.COM must be in the same directory or 'PATH'ed! Also, the remote user is allowed to download the extract file in either ARC, LHARC, PKPAK, or PKZIP formats, so those programs must be available. Okay, now it is time to setup the list of conferences that you want to access. It is primarily the same format as what is found in the AREAS.BBS except that Descriptions are handled upto 12 characters in length and that a set of special symbols are used for additional parameters. Also, there is a field called the ID# field. This field instructs Smlnet which Location# that it should use for keeping 'Last Read' Message pointers. Valid numbers are from 01 to 119 Only! So when you add a conference you must use a Unique Number(01-119) that it not currently in-use by another conference. This is a Unique Reference system and the ID# should NOT be changed once it is assigned. When you re-sort the conferences, you will NOT change ANY of the ID# numbers. Also, you will not change any of the other conference ID# numbers when you delete a Conference. Because of this ID# system can be listed in any order, it is possible for you to resort the conference names when you add or delete conferences. (I always like sorted conference lists...) The basic format is: [ID#:] [Drive:\Path] [DescriptionName] [Symbol] per line ID#: 4 character field terminating with a Space character Drive:\Path terminated with a Space character DescriptionName first 12 characters is recognized Symbol explained below < >, [ ] ID# :number from 01 to 119 :Must be UNIQUE for each conference! :tell Smlnet which field for 'Last Msg' read so that even when the Conference names are added/deleted/moved the 'Last Msg' read pointer field location will stay with that conference. Drive:\Path :must be for a valid subdirectory :must have a space before and after it DescriptionName :first 12 characters are recognized :this name is displayed to the Remote user Symbol :if level is not met, then conference name is not displayed. <SYSOP> symbol instructs the program that this conference is for Sysop-Access Level users only. <####> symbol caller must have a security level equal or greater then this to join conference. #### means upto a 4digit security number. [##] symbol is used for Multizone support This is decide the Origin Net/Nodes to save with the message. Hmm, thats it on the Smlnet.Cnf file. Again, you should be able to model your Config file after the one provided with the new Smlnet files. [[[ RBBS-PC Environment ]]] If you will be running it directly from RBBS, then you need to add NET to your Menu5. NET.BAT reads: DEL TIMEOFF%1.DOR SMLNET %1 Lines 1 and 2 of NET.bat delete the Games Monitor Transfer files, that shouldn't exist if called directly from RBBS. (Safety procedure). Lines 3 calls SmlNet program If you will be running it under Bob Wescott's Monitor, then you need to add to the GAMES.DOR : SmlNet---> Enter/Read/Search thru National Conferences Myself, prefer to create a Macro command so that you can call Smlnet directly from RBBS. So, like use the command N for the caller to access Smlnet. [[[ RunTime with RBBS-PC ]]] To access the program Locally, type SMLNET LOCAL SmlNet can also recognize you are running Locally or COM0 mode if you are running RBBS-PC 15.1x or above If SMLNET 1, or SMLNET 2, or... is typed then it will first read the DORINFO?.DEF file, which it will get its information from. If not found, then it will look for the first section of MESSAGES and the RBBS?PC.DEF files.(But reading the MESSAGES and RBBS?PC.DEF will only work for 15.1A and eariler versions of RBBS.) The Dorinfo?.Def file is the best to make accessible for Smlnet to use. It contains everything that is needed, and has been stable for almost all versions of RBBS since 15.1B. This program will monitor Carrier, and will exit the program whenever it sees that the Carrier has dropped. It can support COM1 and COM2 only without using the Fossil driver. [[[ RunTime with PCBOARD ]]] Will autoconfig between PCBoard verison 12 and 14 .sys formats. ------------------------------------------------------------- For usage on multiple nodes requires Version 14 .SYS file. ------------------------------------------------------------- Command Line Parameters: ============================================================= For: Disable User Security Level or using version 12 .SYS SMLNET PATH\PCBOARD.SYS 1 | | ^sysfile ^COMport ------------------------------------------------------------- For: Activate User Security Levels requires Version 14 .SYS SMLNET PATH\PCBOARD.SYS 1 PATH\USERS | | | ^sysfile COMport^ ^Usersfile ============================================================= Which is: PATH\PCBOARD.SYS - Path and filename of PCBoard.sys file PATH\USERS - Path and filename of PCBoard Users file 1 (or 2) - Com.Port Thank Vernan's War Board at (714) 989-7596 for helping with how to get this program to work with PCBoard. To setup Smlnet, so that it will run with PCBoard, you will need setup a Door Bat file that will then call SMLNET.EXE in this fashion. SMLNET \PATH\PCBOARD.SYS 1 \PATH\PCBOARD.SYS is the path and the name of the .SYS file that you want smlnet, to read to get the Player's Info like their Names, and the time available. 1 (can be 2) is the ComPort number, for the program to use the correct ComPort for Remote Operations. This format must be always used, even if for remote or local use with PCBOARD. You can run in Local mode in 2 ways, either telling PCBOARD you are local, so that it will put Local into the pcboard.sys file, or you can type Smlnet LOCAL. \Path\Users is the path and the name of the PCboard Users file. Smlnet will ONLY read the security level from this file. If you do not want security levels or can create a Version 14 Users file, then leave the \Path\Users section blank. Current version should work automatically between PCBoard 12.x and PC Board 14+ . You must have at least PC Board 14 to run it under multiple nodes. [[[ Function Keys Supported: ]]] Currently only F10 is supported. Chat Mode F10 F10 will interrupt the Command -> prompt and will enter a routine for Chat Mode. If you press the F10 key when Chat is already engaged it will Beep both you and the remote user. Though, You may also send Beeps (ASCII 7) to each other. Either the remote user or the sysop can send the ESC code and Chat will then be terminated. The Timeout default of 4 minutes is not monitored in Chat Mode, but Loss of Carrier is. [[[ Sysop Setup for Remote Caller Message Extraction ]]] Messages selected by the user are appended into a sequential 'EXTRACT' file. This file is downloaded by Shelling to DSZ.COM (by Chuck Forzberg) so, Xmodem, Ymodem(1K Packet), and Zmodem is supported. If you haven't ever tried DSZ.COM, then please treat yourself to this excellent Communication program. Zmodem is excellant over the long distance lines! Basically, you will just need to move DSZ.COM into the same sub-directory has Smlnet.exe occupies. I encourage you to register DSZ.COM for it is the best file transfer program so far as I have seen in ShareWare. The default Extract file is UNR-MAIL.TXT The default Packed file is UNR-MAIL.ARC The Extract,Archive, and Log filenames depend on the Node#. (The first character to the left of the '.' will reflect the node # that the caller is on.) For example: Local Mode UNR-MAIL.TXT ,UNR-MAIL.ARC, SMLNET.LOG Node 1 will have UNR-MAI1.TXT ,UNR-MAI1.ARC, SMLNE1.LOG Node 2 will have UNR-MAI2.TXT ,UNR-MAI1.ARC, SMLNE2.LOG You can choose anyname for the extract file. But, the extension must be .TXT, and no Drive:\Path is allowed for it. The program will use the 'extract' filename that you specify but it will always display 'UNR-MAIL.TXT', and use the 'UNR-MAIL.ARC' for the packing routines. Again, for example for Node #2, the remote caller will see 'UNR-MAIL.TXT' and/or 'UNR-MAIL.ARC' but internally the program will use the filename that is in the SMLNET.CNF file with the Node 2 to the left side of the '.' mark. Probably the best method is to leave the program default to the UNR-MAIL.TXT filename in the SMLNET.CNF file. Smlnet will not allow a remote user to create an 'extract' file that is bigger then the time needed to download the file. BUT, it will allow the remote user to download the 'extract' file no matter how much time he has left. The 'Extract' file is Always re-started upon startup of Smlnet program. And, can also be deleted(re-started) after the remote caller downloads it. [[[ Briefly how I had setup MultiZone on this board ]]] Binkley.CFG Dis-enabled the No Zones Option Parselst.CTL I added MYLIST NODELIST.110 so, that whenever it compiled my normal incomming RBBSlist files, it will also recompile the NodeList.??? that has Zone 1,2, & 3. When I added NodeList.??? in addition to my normal RBBSlist files, the result .DAT files and such are at least 400K in size. Made Directories: MD \Outbound.001 MD \Outbound.002 MD \Outbound.003 in addition to the already current \Outbound that existed for my Zone 8 setup. Normal messages are sent out thru normal mail handling programs such as OMMM, RBBSPACK, or Qmail. So, hence, Smlnet is meant to do only CrashMail, FileRequests, and FileAttaches to everywhere as setup in the smlent.zon file. For the Smlnet side: I modified the Smlnet.ZON file, so that multi-zone was activated. (the first prompt had Y instead of N) I added the info in Smlnet.ZON for where my Zone 1,2 & 3 Outbound subdirectories where. (in the sample .ZON, Zone 1 outbound is setup) When using Smlnet, if you do a Crash, File Attach, or File Request, it will ask you which Zone # Outbound-directory it should put the mail packet in. Normally, you would just press enter if the Dest Zone was the same as yours. If I send it to Zone 1, then I answer it with 1, which then it will save the mail packet in Outbound.001 subdirectory. Nothing else needs to be setup for Multizone. Basically, it just verifies if the net/node exists, and if so, then it will ask you which outbound directory to put the mail packet in, and then it will save the packet in that subdirectory. Hmm, thats it. [[[ Limitations of the Program ]]] This program may have some problems with very large sized messages. Whenever, an individual message may be greater then 10K in size, then the program may error out and exit. (but, suppousedly a message larger then 10K is not allowed anyhow...) This program code logic has been changed so that it is optimized for Size. (so hence the programming structure is now poor, and does not follow good programming logic). (Items that can be changed if needed) A maximum of 9999 Messages in a Base can be accessed. A maximum of 119 Conferences can be accessed. A maximum of 300 lines for each message for Extracting/Saving. (Current Version) This program does not do any type of File or Record Locking, so if you must take proper precautions if operating in a Multi-Tasking / Multi-User environment. Could someone send me some Good DOCS on how to do record/file locking ? BUT, it does a good job on trying to make sure nothing will get scrambled when working with a Multi-Node system. And especially for the Fido-type of message formats (one message per filename, the odds are real low.) ...FILE SHARING is in, but not full File locking. Maximum of 38,400 Baud and 2 Com.Ports, except with Fossil Driver. [[[ Revisions to the Program ]]] Version 1.f: June 1989 Fossil Support Use of the SmlIndex.Dat file which greatly increases the Join/Check speed Use of Smlnet.OFF for setting time ranges that Smlnet should not be in use. (This is for MultiNode systems, that want to insure that no one can access Smlnet, when their Master Node is Renumbering and other such major maitainence on the Echo conferences.) Net and Node values from 0 to 32767. Version 1.e: Apr 1989 Version 1.d: Dec 1988 Version 1.0: October 15, 1988 The very first version of this program. Since this is the very first version of this utility, it probably has some bugs in it. Have fun with the program, it includes about every possible (usefull) command that could be done with the EchoMail conferences. If you need more, just let me know. ══ END OF SMLNET DOCUMENTATION ═════════════════════════════════════════════ ------ Okay, now commercial time !!! for any Unregistered ones -------------- The 1988 software concept so far involves... (As of 6/01/89) 1. SIDROIDS II This Multi-BBS doorgame is undergoing Betatesting. still in vaporware... especially after my harddisk crash... 2. SIDROIDS (Command BattleDroids in a 30,000 cell field, with the use of Messages, Teams, and Scripts that will control your Droid during anothers play period) (Current ShareWare version 2.36. (Registered version also has some more stuff..(2.5x) (PCboard/ RBBS compatible) 3. THAI The UnderGround Thai Lottery - A Lottery Simulation DoorGame (Play the Thailand Lottery...) Current Version 1.4 (A minor program but kinda educational...) (PCboard/ RBBS compatible) 4. SMLNET Small Netmail/EchoMail Editor/Reader (does alot of neat stuff) download message files, keep message pointers, and more! (PCboard/RBBS compatible) 5. SMLMESS Small Message Utility is created for RBBS sysops download message files, keep message pointers, and more! (Egads, another Message Editor?) 6. SMLCALL Small Caller Analyzer - is utility created for RBBS sysops wanting to do simple but effective analyzing on their Callers and System. Remote and Batch Support. Current version 2.3 and more whenever I get a good chance to work on...